Reviewing files that changed from the base of the PR and between c1ebe60 and fea2659.

• src/operator/get-range.ts (1 hunks)

• GitHub Check: Upload results

src/operator/get-range.ts (2)

108-111: Implementation already returned an array - type mismatch existed.

The implementation has always returned Array<PlainBufferRow> via decodePlainBuffer(), identical to how rows is decoded (line 105). The previous type definition of PlainBufferRow | null was incorrect, creating a type-implementation mismatch.

This change fixes the type alignment but introduces a breaking change for consumers who were expecting a single row based on the previous type definition.

---

31-31: I need to search more broadly for how GetRangeResponse is consumed:

Now let me verify how decodePlainBuffer is actually defined and what PlainBufferRow represents:

Let me verify one more time by searching for actual usage patterns of nextStartPrimaryKey in similar TypeScript/Node.js codebases:

Based on my verification using official TableStore documentation and SDK samples, I can now provide the final assessment:

---

The type change is correct and requires no modifications. The official Node.js TableStore SDK shows nextStartPrimaryKey is accessed as an array (e.g., data.nextStartPrimaryKey[0].value, data.nextStartPrimaryKey[1].value), confirming that Array<PlainBufferRow> | null is the appropriate type. This change aligns the TypeScript SDK with the existing implementation and matches the standard pattern across TableStore SDKs. The original review comment's concerns about extracting the first element are unfounded—the array structure correctly represents the multi-column primary key used for pagination.